Product Architecture and Design [DRAFT]

Development Notes

Target Audience: Quantum Software Product Support (SPS) and Sustaining Engineering

Goal: Use this topic to guide you through an in-depth exploration of the architectural components that affect performance.

Contributors

SPS: Mark Higley and Michael Richter
Professional Services (PS):
Sustaining: Mark Reinhardt
Engineering: Jim (Storage Manager) and Brent (File System)
Quality: Eva
Education: Dave Goff

Schedules

**Architecture and Design Schedule**
Milestone	File System	Storage Manger
Kick Off	September 22	September 22
Post RAW Content	September 30	TDB
Team Review	October 17	TDB
Integrate Feedback	October 21	TDB
Internal Review/Edit	October 26	TDB
GO LIVE	October 31	TDB

Overview

This topic examines performance from a product architecture and design perspective. When applying a rational troubleshooting approach to performance-related issues, a thorough explanation of the functional components is a necessary starting point.

Answers to these types of questions provide the raw content for this section:

What is coded in StorNext that impacts performance?
What is tunable and what is not?
- What are the coded hard limits?
- What are the recommended soft limits? (not necessarily coded)
- What is user configurable?
How will I know when a functional component is not working?
- Will the problem be logged?
- Where is the component located?
- What messages will I see?

Resources and References (MOVE THIS SECTION)

For questions, contact dave.goff@quantum.com
Useful documents: \\file01dn\public\Stornext
StorNext Engineering Twiki: http://boris.adic.com/twiki/bin/view/StorNext/WebHome

What's Next?

Configuration Impacts on Performance >